Group account service providing server and method

ABSTRACT

According to one aspect of the present invention, a group account service providing server capable of converting a private account into a group account in real time through a terminal of the host of a comprises: an account management unit configured to convert a first account into a group account when a group account conversion request for the first account of a host of a group is generated; a transaction ledger management unit configured to record change information in a transaction ledger for the group account when the change information including at least one of a transaction occurrence event and an information occurrence event is generated for the group account; a virtual ledger management unit configured to generate a virtual ledger to be mapped to the transaction ledger when the first account is changed to the group account.

TECHNICAL FIELD

The present invention relates to a banking service, and morespecifically, to a mobile banking service.

BACKGROUND ART

Even in the reality of society gradually changing into anindividualistic society, modern people have one or two groups throughthe links of kinship, regional links, and school relations. In order forthese groups to be maintained and developed continuously, funds formanagement of groups are necessarily required.

Generally, in order to manage funds for management of groups, a methodof opening a bank account under a name of a group or a real name of ahost of the group and managing the funds for management of groups usingthe opened bank account is used.

However, in the case in which the bank account is opened under the nameof the group, there is a problem in that a procedure for opening thebank account is strict and complicated because the bylaws or articles ofincorporation of the group are required. In the case in which the bankaccount is opened under the host's real name, there is a disadvantage inthat it is not only inconvenient because the host should visit the bankin person to open an account, and when the host has an account that hasalready been opened at the corresponding bank, it is also inconvenientbecause the host is restricted from opening an additional account or canonly open a limited account with a limit on the transaction amount.

In addition, when the group is operated using the bank account openedunder the host's real name, there is a problem in that inconvenience isincreased because participants of the group may not be able to check thetransaction history of the bank account opened under the host's realname so that the management of the membership fees may become unclear,and because the transaction history of the bank account opened under thehost's real name should be printed out or provided through screencapture in order to share the transaction history of the bank accountopened under the host's real name with the participants of the group.

SUMMARY Technical Problem

Therefore, the present invention is designed to solve the problems andis for providing a group account service providing server in which aprivate account for a host of a group may be converted into a groupaccount in real time through a terminal of the host.

The present invention is also for providing a group account serviceproviding server in which the contents recorded in a transaction ledgerof a group account may be shared between participants of a group and ahost of the group through a virtual ledger which is generated by copyingthe contents recorded in the transaction ledger of the group account.

The present invention is also for providing a group account serviceproviding server in which a participant of a group may be invited to agroup account service through a terminal of a host of the group and theparticipant may be registered as a member for on the group account.

Technical Solution

To solve the above problems, the present invention may include thefollowing configurations.

A group account service providing server includes an account managementunit configured to convert a first account into a group account when agroup account conversion request for the first account of a host of agroup is generated; a transaction ledger management unit configured torecord change information in a transaction ledger for the group accountwhen the change information including at least one of a transactionoccurrence event and an information occurrence event is generated forthe group account; a virtual ledger management unit configured togenerate a virtual ledger to be mapped to the transaction ledger whenthe first account is changed to the group account and copy the changeinformation recorded in the transaction ledger to record the copiedchange information in the virtual ledger when the change information isrecorded in the transaction ledger; and an interface unit configured todisplay the transaction ledger on a first agent installed in a firstterminal of the host and display the virtual ledger on a second agentinstalled in a second terminal of a participant sharing the groupaccount.

A group account service providing method includes converting a firstaccount into a group account in response to a group account conversionrequest for the first account of a host of a group; generating a virtualledger to be mapped to a transaction ledger of the group account;recording change information in the transaction ledger when the changeinformation including at least one of a transaction occurrence event andan information occurrence event is generated for the group account; whenthe change information is recorded in the transaction ledger, monitoringthe transaction ledger and copying and recording the change informationin the virtual ledger; and outputting contents recorded in thetransaction ledger to a first agent installed in a first terminal of thehost and outputting contents recorded in the virtual ledger to a secondagent installed in a second terminal of the participant sharing thegroup account.

Advantageous Effects

According to the present invention, a private account for a host of agroup can be changed to a group account in response to a group accountconversion request generated through a terminal of the host withoutvisiting the bank so that the group account can be easily opened.

Further, according to the present invention, when a transaction historyis recorded in a transaction ledger according to the occurrence of thetransaction history in the group account, the transaction historyrecorded in the transaction ledger is copied and recorded in a virtualledger, the host can know the contents of the group account through thetransaction ledger and a participant of the group can know the contentsof the group account through the virtual ledger, and thus not only thehost but also the participant can check the transaction history in thegroup account in real time. Therefore, a membership fee can be usedtransparently.

Further, the host can share the contents of the group account with theparticipants by providing the contents of the virtual ledger without anyinconvenience, such as printing out the transaction history or capturinga screen to share the transaction history of the group account with theparticipants, and thus the host can conveniently manage the groupaccount.

Further, according to the present invention, the participant who willparticipate in the group account can be registered only by selecting aperson from a list of the persons obtained from a messenger programinstalled in the terminal of the host, and thus the participant can beeasily managed so that the group can be activated.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a group account service providingsystem according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating a configuration of a groupaccount service providing server according to an embodiment of thepresent invention.

FIGS. 3A, 3B, 3C and 3D are views illustrating examples of a groupaccount conversion page displayed through an agent according to anembodiment of the present invention.

FIGS. 4A and 4B are views illustrating examples of a transaction historypage output on a first agent and a second agent according to anembodiment of the present invention.

FIGS. 5A, 5B and 5C are views illustrating examples of a memberregistration request page output on a first agent according to anembodiment of the present invention.

FIG. 5D is a view illustrating an example of a subscription requestmessage output on a second messenger agent according to an embodiment ofthe present invention.

FIG. 5E is a view illustrating an example of a group accountparticipation request page output on a second agent according to anembodiment of the present invention.

FIG. 6A is a view illustrating an example of a group account exit pageoutput on a second agent for a member to exit according to an embodimentof the present invention.

FIG. 6B is a view illustrating an example of a member exit request pageaccording to an embodiment of the present invention.

FIG. 7A is a view illustrating an example of a transaction history pageincluding a membership fee deposit icon output on a second agentaccording to an embodiment of the present invention.

FIG. 7B is a view illustrating an example of a transfer page including adeposit amount input window and a withdrawal account selection windowoutput on a second agent according to an embodiment of the presentinvention.

FIGS. 8A, 8B, 8C and 8D are views illustrating examples of a membershipfee payment history page output on a first agent according to anembodiment of the present invention.

FIG. 9 is a view illustrating an example of an intro page for providinga banking service when a second agent is executed according to anembodiment of the present invention.

FIG. 10 is a flowchart illustrating a group account service providingmethod according to an embodiment of the present invention.

FIG. 11 is a flowchart illustrating a method of performing a participantregistration procedure according to an embodiment of the presentinvention.

DETAILED DESCRIPTION

In this specification, when reference numerals are assigned tocomponents of each drawing, it should be noted that, even when the samecomponents are illustrated in different drawings, the same numerals areassigned to the same components whenever possible.

Meanwhile, the meaning of the terms described in this specificationshould be understood as follows.

Elements of the invention referred to as singular may number one ormore, unless the context clearly indicates otherwise. The terms first,second, etc. are used to distinguish one component from anothercomponent, and the scope of the present invention is not limited tothese components.

It will be further understood that the terms “comprise,” “comprising,”“include,” and/or “including,” do not preclude the presence or additionof one or more other features, numbers, steps, operations, components,parts and/or combinations thereof.

When the term “at least one” is used, it should be understood to includeall possible combinations of one or more of the associated listed items.For example, “at least one of a first item, a second item, and a thirditem” means each of the first item, the second item, and the third item,and means a combination of all items that may be presented from two ormore of the first item, the second item, and the third item.

Hereinafter, embodiments of the present invention will be described withreference to the accompanying drawings.

FIG. 1 is a diagram illustrating a group account service providingsystem according to an embodiment of the present invention. Asillustrated in FIG. 1, a group account service providing system 10according to the embodiment of the present invention includes userterminals 50 and a group account service providing server 100.

The user terminals 50 communicate with the group account serviceproviding server 100 through a network to provide a group accountservice to users. To this end, a banking agent (hereinafter, referred toas an “agent”) is installed in the user terminal 50. The agent receivesa banking request from the user and transmits the banking request to thegroup account service providing server 100 to allow the banking requestreceived from the user to be processed by the group account serviceproviding server 100.

For example, when receiving an account opening request or a transferrequest from the user, the agent transmits the received account openingrequest or the transfer request to the group account service providingserver 100 to allow the group account service providing server 100 toopen an account or transfer an amount requested to be transferred.

In an embodiment, when a group account related request including a groupaccount conversion request or a participant registration request isreceived from a host who establishes a group, a first agent installed ina first terminal 53 of the host may provide the group account relatedrequest to the group account service providing server 100 to allow thegroup account service providing server 100 to provide a group accountservice.

Meanwhile, a second agent installed in a second terminal 56 of aparticipant who wants to participate in the group joins in the groupaccount service in response to the participant registration requesttransmitted from the first agent, and thus the group account service isprovided to the participant through the second agent. In FIG. 1,although the second terminal is illustrated as a single terminal, thisis only exemplary, and a plurality of second terminals may be provided.The participant may share a transaction history of the group accountwith the host in real time through the second agent.

The group account service providing server 100 provides the groupaccount service to the host through the first agent and to theparticipant through the second agent. Hereinafter, the group accountservice providing server 100 will be described in detail with referenceto FIG. 2.

FIG. 2 is a block diagram illustrating a configuration of the groupaccount service providing server 100 according to the embodiment of thepresent invention. As illustrated in FIG. 2, the group account serviceproviding server 100 includes an account management unit 210, atransaction ledger management unit 220, a transaction ledger 230, avirtual ledger management unit 240, a virtual ledger 250, a participantmanagement unit 260, a deposit and withdrawal management unit 270, asearch unit 280, and an interface unit 290.

When receiving a group account conversion request from the first agent,the account management unit 210 converts a first account previously heldby the host into a group account. In an embodiment, the group accountconversion request may include information about the first account whichis a subject to be converted, setting information for group account tobe generated, and additional information for the group account.

In this case, the group account conversion request may be generated bythe first agent installed in the first terminal 53. Hereinafter, theprocess in which the group account conversion request is generated bythe first agent will be described in detail with reference to FIGS. 3Ato 3C.

FIG. 3A is a view illustrating a group account opening request page,FIG. 3B is a view illustrating an account conversion request page, andFIGS. 3C and 3D are views illustrating a group account settinginformation input page.

When the host executes the first agent through the first terminal 53, anintro page for providing the banking service may be provided through thefirst agent, and when the host requests to open the group accountthrough various routes provided on the intro page, the group accountopening request page as illustrated in FIG. 3A may be provided throughthe first agent. For example, when the host selects a menu “recommended”on the intro page, a page including a sub menu “group account” may beprovided through the first agent, and when the host selects the sub menu“group account,” the group account opening request page as illustratedin FIG. 3A may be provided through the first agent.

When a start now button 310 on the group account opening request pageillustrated in FIG. 3A is selected by the host, the account conversionrequest page as illustrated in FIG. 3B is provided through the firstagent.

The first agent receives information about the first account to beconverted into the group account from the host through an accountselection menu 320 on the account conversion request page. In anembodiment, the first account may be a general account opened under areal name of the host. For example, the first account may be a depositand withdrawal account opened under the real name of the host. In thiscase, the deposit and withdrawal account may be not only a normalaccount but also a limited account with a limit on the transactionamount.

Further, when a new account button 330 is selected by the host who doesnot have any account, pages related to an account opening process foropening a new account may be sequentially provided through the firstagent, thereby guiding the new account opening.

Further, when a button 340 for processing the transaction name withasterisks is selected by the host, the account management unit 210 mayreceive a masking processing request and set masking processing for thegroup account. In this case, information about the masking processingmay be included in the additional information for the group account.

When the account is selected or the account opening is completed, thegroup account setting information input pages as illustrated in FIGS. 3Cand 3D are provided through the first agent. The host may input thesetting information for the group account including a name of the group,a category of the group, and the like through the group account settinginformation input pages. In FIGS. 3C and 3D, although the name of thegroup and the category of the group are illustrated as being inputthrough the group account setting information input pages, this is onlyexemplary, and additional information including a membership fee, amembership fee payment date, and the like may be input through the groupaccount setting information input pages.

When the group account conversion request is generated through theprocess illustrated in FIGS. 3A to 3D, the first agent transmits thegenerated group account conversion request to the account managementunit 210.

Meanwhile, the pages as illustrated in FIGS. 3A to 3D may be provided tothe first agent through the interface unit 290 to be described below.

Referring to FIG. 2 again, when the account management unit 210 receivesthe group account conversion request from the first agent, the accountmanagement unit 210 may convert the first account, which is a subject tobe converted into the group account, into the group account, notify thetransaction ledger management unit 220 of the conversion to allow thetransaction ledger management unit 220 to record information that thefirst account is changed to the group account, and the settinginformation and the additional information, which are included in thegroup account conversion request, in the transaction ledger 230 for thegroup account.

In an embodiment, when the account management unit 210 converts thefirst account into the group account, the account management unit 210may assign a safe account number different from a real account number ofthe first account to the group account. In the present invention, thereason for assigning the safe account number different from the realaccount number of the first account to the group account is because,according to the present invention, the first account opened under thereal name of the host is converted into the group account and the groupaccount is shared with the participant so that the real account numberof the first account may be revealed to the participant and personalinformation of the host may be leaked to the outside.

According to the embodiment, a real account number 410 a of the firstaccount may be provided to the host on the first agent as illustrated inFIG. 4A, and a safe account number 410 b may be revealed to theparticipant on the second agent as illustrated in FIG. 4B.

However, in another embodiment, the safe account number may be revealedto both of the host and the participant through the first and secondagents, or both of the real account number of the first account and thesafe account number may be provided to the host on the first agent andthe safe account number may be provided to the participant on the secondagent.

When the account management unit 210 assigns the safe account number tothe group account, the account management unit 210 may notify thetransaction ledger management unit 220 of the assigned safe accountnumber so that the transaction ledger management unit 220 may map thesafe account number with the real account number of the first accountand record.

Meanwhile, when the account management unit 210 according to the presentinvention receives a group account dividing request for the groupaccount for which the conversion into the group account is completedfrom the host through the first agent, the account management unit 210may generate a child account whose parent account is the group account.Specifically, when the account management unit 210 receives the groupaccount dividing request from the first agent, the account managementunit 210 opens the child account whose parent account is the groupaccount and which has at least some deposit amount of the parent accountas a deposit amount thereof. Accordingly, the host may more convenientlymanage reserve funds for the group as compared to the case of managingreserve funds for the group by opening a separate account.

In an embodiment, the account management unit 210 may allow the depositamount of the child account to be set within a predetermined maximumamount among the deposit amount of the parent account and may assign thefirst interest rate to the deposit amount of the parent account andassign the second interest rate different from the first interest rateto the deposit amount of the child account. In this case, the secondinterest rate may be set to be higher than the first interest rate. Asdescribed above, in the embodiment of the present invention, the accountmanagement unit 210 may assign an interest rate higher than that of thedeposit amount of the parent account to the deposit amount of the childaccount, thereby guiding the host to open the child account and operatethe reserve funds for the group.

According to the embodiment, the account management unit 210 maygenerate a plurality of child accounts for one parent account inresponse to the request of the user. In this case, the accountmanagement unit 210 separates and manages the deposit amount of theparent account and the deposit amount of each of the plurality of childaccounts, respectively.

When the account management unit 210 generates at least one childaccount whose parent account is the group account, the accountmanagement unit 210 may notify the transaction ledger management unit220 of the generation of the child account to allow the transactionledger management unit 220 to record information on whether the childaccount is generated for the group account and record information aboutthe deposit amount of the group account and the child account in thetransaction ledger.

When the generation of the child account whose parent account is thegroup account is completed in response to the group account dividingrequest, menus 420 a and 420 b indicating whether the child account isgenerated may be output through the first and second agents asillustrated in FIGS. 4A and 4B. In this case, the menus 420 a and 420 bindicating whether the child account is generated may include thedeposit amount of the child account.

Referring to FIG. 2 again, when the first account is converted into thegroup account by the account management unit 210, the transaction ledgermanagement unit 220 records the content of an event in the transactionledger for the group account when the event occurs for the groupaccount. In an embodiment, the transaction ledger for the first accountmay be used as the transaction ledger for the group account as it is orthe transaction ledger for the group account may be newly generated.

In an embodiment, the event for the group account may include at leastone of a transaction occurrence event and an information occurrenceevent. The transaction occurrence event may be a deposit event or awithdrawal event for the group account. When the transaction occurrenceevent such as the deposit event or the withdrawal event occurs for thegroup account, the transaction ledger management unit 220 may record thecontent of the event, which includes a transaction date and time, anabstract, a transaction amount, and a balance, in the transaction ledger230.

The information occurrence event may include at least one of memorelated to deposit or withdrawal, a tag, registration or withdrawalinformation of the participant, an announcement related to the group, aDutch treat payment request, the setting information for the groupaccount, and the additional information for the group account. Here, thetag is for distinguishing a representative transaction and, for example,when payment is made using a check card, a symbol “#check card” may bedisplayed. The setting information may include a name of the group, acategory of the group, information about a messenger profile, amembership fee, and a membership fee payment date. The additionalinformation may include information about masking processing,information on whether the child account is generated, information aboutthe child account, and information about the safe account number.

Meanwhile, when the transaction ledger management unit 220 receives aDutch treat payment request from the first agent by the host, thetransaction ledger management unit 220 records the Dutch treat paymentrequest in the transaction ledger 230. The Dutch treat payment requestincludes an amount spent, the number of the members including the hostand the participants to share the amount spent, and an amount shared byeach member. For example, when the amount spent and the number ofmembers to share the amount spent are input by the host through a menu(not illustrated) that is output when a Dutch treat payment request icon(not illustrated) is selected by the host through the first agent, theamount shared by each member may be automatically calculated so that theDutch treat payment request may be generated.

The content recorded in the transaction ledger 230 by the transactionledger management unit 220 is output on the first agent by the interfaceunit 290.

The transaction occurrence event and the information occurrence eventare recorded in the transaction ledger 230 by the transaction ledgermanagement unit 220. Here, the transaction ledger 230 may be implementedin the form of a database.

When the first account is converted into the group account by theaccount management unit 210, the virtual ledger management unit 240generates the virtual ledger 250 for the group account, copies thecontent recorded in the transaction ledger 230, and records the copiedcontent in the virtual ledger 250.

In the present invention, the reason for generating the virtual ledgerthrough the virtual ledger management unit 240 is because the host maydirectly assess the transaction ledger 230 but the participant may notdirectly assess the transaction ledger for the group account, which isan account of another person, and the virtual ledger in which thecontent recorded in the transaction ledger 230 is copied and recordedmay be generated so that the participant may read the virtual ledger,and thus the participant may feel substantially the same as when readingthe transaction ledger.

The virtual ledger management unit 240 may monitor change information ofthe transaction ledger 230 in real time, and when it is determined thata change occurs in the transaction ledger 230, the virtual ledgermanagement unit 240 records the change information occurred in thetransaction ledger 230 in the virtual ledger 250. Specifically, as aresult of the monitoring of the transaction ledger 230, when atransaction occurrence event is newly recorded in the transaction ledger230, the virtual ledger management unit 240 copies the newly recordedtransaction occurrence event to record the newly recorded transactionoccurrence event in the virtual ledger 250. Further, when, as a resultof the monitoring of the transaction ledger 230, an informationoccurrence event is newly recorded in the transaction ledger 230, thevirtual ledger management unit 240 copies the newly generatedinformation occurrence event to record the newly generated informationoccurrence event in the virtual ledger 250.

The content recorded in the virtual ledger 250 by the virtual ledgermanagement unit 240 is output on the second agent by the interface unit290.

Meanwhile, when the transaction ledger management unit 220 uses thetransaction ledger for the first account as the transaction ledger 230for the group account as it is, the virtual ledger management unit 240may copy and record the transaction occurrence events and theinformation occurrence events that occurred after the time when thefirst account is converted into the group account. Accordingly, sincethe participants may check only the transaction occurrence event and theinformation occurrence event that occurred after the time when the firstaccount is converted into the group account, it is possible to preventthe pieces of information generated during the period when the groupaccount is used privately by the host from being shared with theparticipants and prevent the personal information of the host fromleaking.

In the virtual ledger 250, the transaction occurrence events and theinformation occurrence events which are recorded in the transactionledger 230 are recorded by the virtual ledger management unit 240. Here,the virtual ledger 250 may be implemented in the form of a database.

As described above, according to the present invention, when thetransaction history is recorded in the transaction ledger according tothe occurrence of the transaction history of the group account, thevirtual ledger management unit may copy the transaction history recordedin the transaction ledger and record the copied transaction history inthe virtual ledger so that the content recorded in the virtual ledgermay be provided to the participants and not only the host but also theparticipants may check the transaction history in the group account inreal time.

The participant management unit 260 registers at least one personselected by the host among the persons registered in a first messengeragent as the participant. To this end, the first agent obtains a list ofthe persons registered in the first messenger agent by communicatingwith the first messenger agent and provides the obtained list of thepersons to the host through the first agent.

The participant management unit 260 may generate a participantregistration request for registering a target person as the participantby selecting at least one person among the list of the persons outputthrough the first agent by the host.

For example, as illustrated in FIGS. 5A to 5C, when the host executesthe first agent through the first terminal, the intro page for providingthe banking service may be provided on the first agent, and when thehost requests to register the participant through various routesprovided on the intro page, a participant invitation page may beprovided on the first agent as illustrated in FIG. 5A.

As illustrated in FIG. 5A, a participant invitation icon 510 is outputon the first agent by the interface unit 290. When the host selects theparticipant invitation icon 510, a participant selection page in whichthe persons registered in the first messenger agent are displayed on thefirst agent as illustrated in FIG. 5B is displayed.

Further, unlike that illustrated in FIG. 5A, it is possible to providethe participant selection page as illustrated in FIG. 5B even through apage having a “participant invitation” icon. The page may be providedthrough the first agent after the host generates the group accountconversion request.

In this case, as illustrated in FIG. 5B, check icons 522 are output onthe first agent by the interface unit 290 so that the host may selectthe persons to be invite as the participants. In this case, the checkicon 522 for an uninvited person may be output in an activated status sothat selection is possible, but the check icon 522 for a person who isalready invited as the participant but is waiting to be accepted or fora previously registered person as the participant may be output in adeactivated status so that selection is not possible. Further, in orderto distinguish the person is waiting to be accepted from the previouslyregistered person, an acceptance pending icon 524 may be output for thepersons who is already invited but is waiting to be accepted, and aparticipating icon 526 may be output for the previously registeredperson as the participant.

When the host selects at least one of the check icons 522 for thepersons registered in the first messenger agent and selects aninvitation icon 530, a participant invitation completion page isdisplayed on the first agent as illustrated in FIG. 5C. In this case,the participant management unit 260 receives the participantregistration request from the first agent, generates a group accountsubscription request message, and transmits the generated group accountsubscription request message to the second agent and a second messengeragent.

When the participant management unit 260 receives the participantregistration request from the first agent, the participant managementunit 260 generates the group account subscription request message forregistering the target person to the group account and transmits thegenerated group account subscription request message to the secondmessenger agent installed in the second terminal 56 of the targetperson.

For example, as illustrated in FIG. 5D, when the participant managementunit 260 transmits the group account subscription request message to theperson to be registered as the participant through the second messengeragent and the person to be registered as the participant selects aninvitation acceptance icon 540 on the second messenger agent, the secondagent is executed and the group account participation request page isoutput on the second agent as illustrated in FIG. 5E.

Unlike that illustrated in FIG. 5D, the person to be registered as theparticipant executes the second agent and selects the group accountsubscription request message provided on the second agent so that thegroup account participation request page may be output as illustrated inFIG. 5E.

When receiving an account subscription acceptance message from thesecond agent installed in the second terminal 56, the participantmanagement unit 260 registers the target person as the participant forthe group account. In this case, when the group account subscriptionrequest message output on the second messenger agent is selected by thetarget person and the second agent is run, and when the accountsubscription is accepted by the target person through the second agent,the account subscription acceptance message is generated.

For example, as illustrated in FIG. 5E, when the target person to beregistered as the participant selects acceptance icon 550, theparticipant management unit 260 receives the account subscriptionacceptance message from the second agent while a message indicating thatthe group account invitation is accepted is displayed on the secondagent, and the participant management unit 260 registers the targetperson who accepts the account subscription as the participant.

In the above-described embodiment, the participant management unit 260is described as transmitting the group account subscription request tothe second messenger agent of the target person. However, in a modifiedembodiment, the participant management unit 260 may directly transmitthe group account subscription request to the second agent of the targetperson. In this case, the account subscription acceptance message may begenerated when the account subscription is accepted by the target personafter the group account subscription request message output on thesecond agent is selected by the target person.

When the participant management unit 260 registers the participant, theparticipant management unit 260 may notify the transaction ledgermanagement unit 220 of the registration of the participant so that theinformation about the registered participant may be recorded in thetransaction ledger 230 by the transaction ledger management unit 220.

In an embodiment, the participant management unit 260 may collectivelyregister all the corresponding persons for the participant registrationrequest for all persons registered in a chat room opened on the firstmessenger agent as the participants.

Specifically, when receiving the participant registration request forall the persons registered in the chat room opened on the firstmessenger agent from the first agent, the participant management unit260 transmits the group account subscription request message to thesecond messenger agents installed in the second terminals of the targetpersons included in the participant registration request. When thetarget persons select the group account subscription request message toperform the account subscription acceptance through the second agents,the participant management unit 260 may register the correspondingtarget persons as the participants. In this case, each of the targetpersons may select the group account subscription request messagetransmitted to the second agent to perform the account subscriptionacceptance or may select the group account subscription request messagetransmitted to the second messenger agent and execute the second agentto perform the account subscription acceptance.

Meanwhile, the participant management unit 260 may receive informationabout a messenger profile of the host and information about a messengerprofile of the participant through first agent and record them in thetransaction ledger 230. The information about the messenger profile ofthe host and the information about the messenger profile of theparticipant may be obtained from the first messenger agent. In anembodiment, the information about the messenger profile of the host andthe information about the messenger profile of the participant may beobtained from the first messenger agent by the first agent incommunication with the first messenger agent and be transmitted to theparticipant management unit 260, and the participant management unit 260may transmit the information about the messenger profile of the host andthe information about the messenger profile of the participant to thetransaction ledger management unit 220, and thus the transaction ledgermanagement unit 220 may record the information about the messengerprofile of the host and the information about the messenger profile ofthe participant in the transaction ledger 230.

In this case, the first messenger agent may refer to a social networkingservice (SNS) application or short message service (SMS) application,through which messages are transmitted, and the information about themessenger profile may include the name of the host or the name of theparticipant and a profile picture of the host or a profile picture ofthe participant.

In the above-described embodiment, the participant management unit 260is described as performing a function of registering the participant whowill participate in the group account service. In another embodiment,the participant management unit 260 may additionally perform a functionof exiting the registered participant. Specifically, when receiving aparticipant exit request from the second agent, the participantmanagement unit 260 allows a target participant who is the target of theexit request to from the group account. The participant management unit260 may transmit the information about the target participant whorequests to exit to the transaction ledger management unit 220 to allowthe transaction ledger management unit 220 to record the withdrawalinformation about the corresponding participant.

For example, as illustrated in FIG. 6A, when a menu screen of the groupaccount, which includes a first icon 510 for exiting from the groupaccount, is provided through the second agent and the first icon 610 isselected by the participant, the participant exit request page isprovided as illustrated in FIG. 6B. When a second icon 620 for exitingfrom the group account included in the participant exit request page isselected by the participant, the participant exit request is generatedand transmitted to the participant management unit 260 by the secondagent. Accordingly, the participant management unit 260 performs exitprocessing for the corresponding participant.

Referring to FIG. 2 again, the deposit and withdrawal management unit270 processes a deposit event or a withdrawal event occurring for thegroup account in response to the request of the first agent. Inparticular, according to the present invention, the deposit andwithdrawal management unit 270 may check whether a member (the host orthe participant) registered on the group account deposits the membershipfee by referring to the transaction ledger 230 and may generate andtransmit a membership fee payment message to the member whose membershipfee is not deposited.

Specifically, when a preset membership fee payment date arrives, thedeposit and withdrawal management unit 270 checks the transaction ledger230 to determine the member for which the deposit event does not occuron the membership fee payment date. Thereafter, the deposit andwithdrawal management unit 270 generates the membership fee paymentmessage for guiding the membership fee payment and transmits thegenerated membership fee payment message to the first or second agent ofthe determined member or to the first or second messenger agent of thedetermined member. In this case, the membership fee payment message mayinclude the membership fee payment date, the membership fee to be paid,and the name of the member.

In an embodiment, when a membership fee payment request is generatedfrom the member, the deposit and withdrawal management unit 270 maywithdraw an amount according to a preset transfer condition from thewithdrawal account of the member according to the preset transfercondition without setting a separate transfer condition andautomatically deposit the amount into the group account. In this case,the preset transfer condition refers to a transfer condition in whichthe number for account to be deposited the amount is set as the accountnumber of the group account and the deposit amount is set as the presetmembership fee.

In the above-described embodiment, both of the number for account to bedeposited the amount and the deposit amount are described as being setthrough the preset transfer condition, but in another embodiment, onlythe number for account to be deposited the amount may be automaticallyset as the account number of the group account under the preset transfercondition and the deposit amount may be input from the member.

For example, when the participant selects a “group account” menu on theintro page, a transaction history page including a membership feedeposit icon 710 is provided through the second agent as illustrated inFIG. 7A. When the membership fee deposit icon 710 is selected by theparticipant, a transfer page, which includes a deposit amount inputwindow 720 and a withdrawal account selection window 725, is provided asillustrated in FIG. 7B. After the deposit amount is input to the depositamount input window 720 by the participant and the selection of thewithdrawal account is completed in the withdrawal account selectionwindow 725, when a transfer icon 730 is selected, the membership feepayment request is generated. When receiving the membership fee paymentrequest, the deposit and withdrawal management unit 270 withdraws thedeposit amount input to the deposit amount input window 720 from thewithdrawal account selected in the withdrawal account selection window725 and transfers the withdrawn amount to the group account.

Referring to FIG. 2 again, the deposit and withdrawal management unit270 may withdrawal the membership fee from the withdrawal account set bythe member on the preset membership fee payment date in response to amembership fee automatic transfer request set by the member andtransfers the withdrawn membership fee to the group account.

Meanwhile, when a Dutch treat payment icon provided through the firstand second agents of the members is selected by the member, the depositand withdrawal management unit 270 generates a Dutch treat paymentrequest, withdrawals a shared amount included in the Dutch treat paymentrequest from the withdrawal account set by the member in response toDutch treat payment request, and deposits the shared amount to the groupaccount. In this case, the deposit and withdrawal management unit 270may check the shared amount included in Dutch treat payment request fromthe Dutch treat payment request registered in the transaction ledger230.

As described above, when the Dutch treat payment icon is selected by themember, the deposit and withdrawal management unit 270 automaticallysets the amount to be withdrawn and the deposit account, and thusconvenience may be increased when it is performed to transfer based onthe Dutch treat.

The search unit 280 searches a membership fee payment history recordedin the transaction ledger and classifies and provides a result of thesearch according to at least one of the membership fee payment date andthe name of the member. Here, the membership fee payment date may beclassified by month or year. For example, the search unit 280 mayclassify the membership fee payment history into the membership fee forthis month, last month, or this year. As another example, the searchunit 280 may classify the membership fee payment history into themembership fee for this month and the accumulated membership fee.

In an embodiment, when receiving a membership fee payment search requestgenerated by the host from the first agent, the search unit 280 mayprovide the search result corresponding to the membership fee paymentsearch request to the host through the first agent. In this case, themembership fee payment search request may include the membership feepayment date or the name of the member to be searched.

When the search result is generated, the search unit 280 may generatethe generated search result in the form of a message and provide thegenerated search result to the participant through the second messengeragent or the second agent.

When a “membership fee status” icon 810 is selected by the host on theaccount management page, which includes the “membership fee status” icon810, as illustrated in FIG. 8A, the search unit 280 provides amembership fee deposit status page, which includes the membership feedeposit history for each member as illustrated in FIG. 8B, to the hostthrough the first agent. As illustrated in FIG. 8B, it can be seen thatthe membership fee deposit history is classified into the membership feedeposit for this month and the accumulated membership fee deposit andthat the membership fee deposit history is classified and provided bythe name of each member. Here, the accumulated membership fee depositmay refer to the membership fee accumulated from the opening date of thegroup account to the present.

When a first message card send button 820 is selected by the host on themembership fee deposit status page as illustrated in FIG. 8B, the searchunit 280 generates a search result which includes the membership feedeposit status of all the members in the form of a message asillustrated in FIG. 8C and provides the search result to each memberthrough the second agent or the second messenger agent.

As another example, when any one member 830 among the members isselected by the host on the membership fee deposit status page asillustrated in FIG. 8B, the search unit 280 provides the membership feedeposit status page which includes the membership fee deposit history ofthe corresponding member as illustrated in FIG. 8D to the host throughthe first agent. As illustrated in FIG. 8D, it can be seen that themembership fee deposit history of the corresponding member generatedduring a predetermined period of time is classified for each day andprovided.

When a second message card send button 840 is selected by the host onthe membership fee deposit status page as illustrated in FIG. 8D, thesearch unit 280 generates a search result which includes the membershipfee deposit status of the corresponding member in the form of a messageand provides the search result to the corresponding member through thesecond agent or the second messenger agent.

Referring to FIG. 2 again, the interface unit 290 provides the contentof the transaction ledger 230 to the host through the first agent andprovides the content of the virtual ledger 250 to the participantthrough the second agent.

That is, according to the present invention, the interface unit 290provides the content of the transaction ledger 230 to the host andprovides the content of the virtual ledger 250 to the participant sothat the host and the participant may share the content of thetransaction ledger 230 for the group account in real time.

In an embodiment, when masking processing for the group account is setby the account management unit 210, the interface unit 290 may mask sometransaction occurrence events recorded in the virtual ledger and providethe masked transaction occurrence events to the participant through thesecond agent. A target of the masking processing may be at least aportion of the abstract included in the transaction occurrence event.

That is, since the interface unit 290 directly provides the content ofthe transaction ledger to the first agent of the host, the transactionhistory is provided in a non-masked status on the first agent whereas,since the interface unit 290 provides the content of the virtual ledgerto the second agent of the participant, at least some transactionhistory is provided in a masked status on the second agent.

In the present invention, the reason for providing the unmaskedtransaction history on the first agent and providing the maskedtransaction history on the second agent is because the group account isshared with the plurality of participants so that the personalinformation of the host or the participant may be unintentionallyexposed when the unmasked transaction history is provided to all theparticipants.

For example, in a transaction history 440 a read by the host through thefirst agent as illustrated in FIG. 4A, all pieces of information areprovided in an unmasked status whereas, in a transaction history 440 bread by the participant through the second agent as illustrated in FIG.4B, information may be provided in a status in which the second letterof the abstract is masked.

In FIG. 4B, although only the second letter of the abstract isillustrated as being masked, the first or third letter of the abstractmay be masked or all the letters of the abstract may be masked.

Meanwhile, the interface unit 290 may output messenger profileinformation 450 a about the members recorded in the transaction ledgeror the virtual ledger on the first or second agent in the form of thesame as that illustrated in FIG. 4A. As illustrated in FIG. 4A, theprofile pictures of the host and the participant may be output as themessenger profile information 450 a, and the profile pictures may bearranged sequentially starting from the host in the order of theparticipants who joined the group account. In an embodiment, the profilepictures of the host and the participant may be arranged so that atleast a region 460 overlaps as illustrated in FIG. 4A.

Meanwhile, when the number of the host and the participants is greaterthan or equal to a reference number, the profile pictures of theparticipants and the host may be displayed up to the number of theprofile pictures less than to the reference number without change, andthe profile pictures of the participants and the host in which thenumber of the profile pictures is greater than or equal to the referencenumber may be replaced with one predetermined symbol and displayed. Inan embodiment, as illustrated in FIG. 4A the profile picture may bereplaced with a symbol 470, in which “. . . ” is placed in a circle, anddisplayed.

In FIGS. 4A and 4C, the profile pictures are illustrated as being outputas the information about the messenger profiles of the host and theparticipant, but this is only exemplary, and the names or nicknames ofthe host and the participant may be displayed as the information aboutthe messenger profiles. Further, the profile pictures may be arranged inrandom order, and the profile pictures of the host and all theparticipants may be output regardless of the reference number.

Meanwhile, the interface unit 290 may display the group account andother accounts except for the group account on the first and secondagents in different forms or may separate and display the group accountand other accounts except for the group account in different regions.For example, the group account and the other accounts may be displayedin different colors or, as another example, the information about thegroup account may be displayed in a first region and the informationabout the other accounts except for the group account may be displayedin a second region. In an embodiment, the first region may be a regionlocated below the second region, and the second region may be set tohave a size greater than that of the first region. Accordingly, thevisibility of the other accounts may be increased as compared to thegroup account.

In the above-described embodiment, when there are a plurality of groupaccounts, the interface unit 290 may sequentially place the groupaccounts in the second region in the order in which the group accountsare opened.

For example, as illustrated in FIG. 9, the interface unit 290 places thegroup account in a first region 903 and places the other accounts in asecond region 906 located above the first region 903.

Further, when there are first and second group accounts, the interfaceunit 290 may place the first and second group accounts in the secondregion by overlapping some regions in the order in which the groupaccounts are opened. The first account opened first may be placed at thefront end, and the second account may be placed at the rear end of thefirst account in the form in which some regions overlap.

In this case, the interface unit 290 may additionally provide a groupaccount unfold icon, and thus the first and second accounts whichoverlap may be unfolded and displayed not to overlap a region differentfrom the second region when the group account unfold icon is selected bythe member.

Further, the group account fold icon 910 is provided while the first andsecond accounts are unfolded and displayed, and thus the first andsecond accounts which are unfolded are again placed so that some regionsin the second region overlap each other when the group account fold icon910 is selected by the member.

In FIG. 9, a group account fold icon 910 is illustrated, but this isonly exemplary. When the group account unfold icon is selected, thegroup account unfold icon is changed to the group account fold icon 910,and when the group account fold icon 910 is selected, the group accountfold icon 910 is changed to the group account unfold icon.

Hereinafter, a group account service providing method according to thepresent invention will be described in detail with reference to theaccompanying drawings.

FIG. 10 is a flowchart illustrating a group account service providingmethod according to an embodiment of the present invention. The groupaccount service providing method illustrated in FIG. 10 may be performedby the group account service providing server illustrated in FIG. 2.

The group account service providing server receives a group accountconversion request from a first agent installed in a first terminal(S1010). The group account conversion request is for conversing a firstaccount of a host to a group account. In an embodiment, the groupaccount conversion request may include information about the firstaccount which is a subject to be converted, a setting information aboutthe group account to be generated, and additional information for thegroup account.

When the group account service providing server receives the groupaccount conversion request from the first agent, the group accountservice providing server converts the first account, which is a subjectto be converted, into the group account (S1020).

In an embodiment, when converting the first account into the groupaccount, the group account service providing server may assign a safeaccount number different from a real account number for the firstaccount to the group account. In the present invention, the reason forassigning the safe account number different from the real account numberfor the first account to the group account is because, according to thepresent invention, the first account opened under the real name of thehost is converted into the group account and the group account is sharedwith participants so that the real account number for the first accountmay be revealed to the participants and personal information of the hostmay be leaked to the outside. In this case, the group account serviceproviding server may output the real account number for the firstaccount on the first agent and output the safe account number on asecond agent installed in a second terminal of the participant.

Although not illustrated in FIG. 10, if the group account serviceproviding server receives a group account dividing request from thefirst agent, the group account service providing server may open a childaccount whose parent account is the group account and which has at leastsome deposit amount of the parent account as a deposit amount thereofwhen the group account service providing server converts the firstaccount into the group account. In this case, the group account serviceproviding server may assign a first interest rate to the deposit amountof the parent account and assign a second interest rate different fromthe first interest rate to the deposit amount of the child account. Thesecond interest rate may be set to be higher than the first interestrate.

When the first account is converted into the group account, the groupaccount service providing server generates a virtual ledger for thegroup account (S1030). In the present invention, the reason forgenerating the virtual ledger for the group account is because the hostmay directly assess the transaction ledger but the participant may notdirectly assess the transaction ledger for the group account, which isan account of another person, and the virtual ledger in which thecontent recorded in the transaction ledger is copied and recorded may begenerated so that the participant may read the virtual ledger, and thusthe participant may feel substantially the same as when reading thetransaction ledger.

The group account service providing server determines whether changeinformation about the group account is generated (S1040). The groupaccount service providing server records the generated changeinformation when the change information about the group account isgenerated in the transaction ledger (S1050). In an embodiment, thechange information about the group account may include at least one of atransaction occurrence event and an information occurrence event.

The transaction occurrence event may be a deposit event or a withdrawalevent for the group account. When the transaction occurrence event suchas the deposit event or the withdrawal event occurs for the groupaccount, the group account service providing server may record thecontent of the event, which includes a transaction date and time, anabstract, a transaction amount, and a balance in the transaction ledger.

The information occurrence event may include at least one of memorelated to deposit or withdrawal, a tag, registration or withdrawalinformation of the participant, announcement related to the group, aDutch treat payment request, setting information about the groupaccount, and additional information for the group account. Here, the tagis for distinguishing a representative transaction and, for example,when payment is made using a check card, a symbol “#check card” may bedisplayed. The setting information for the group account may include aname of the group, a category for the group, information about amessenger profile, a membership fee, and a membership fee payment date.The additional information for the group may include information aboutmasking processing, information on whether the child account isgenerated, information about the child account, and information aboutthe safe account number. Further, the information about the maskingprocessing represents a request to mask some transaction occurrenceevents (e.g., at least some abstracts) recorded in the virtual ledger.In the present invention, the reason for performing the maskingprocessing on some of the transaction occurrence events recorded in thevirtual ledger according to the information about the masking processingis because the group account is shared with the plurality ofparticipants so that the personal information of the host or theparticipant may be unintentionally exposed when the unmasked transactionhistory is provided to all the participants.

The group account service providing server monitors whether the changeinformation is recorded in the transaction ledger (S1060), and when itis determined that the change information is recorded in the transactionledger, the group account service providing server copies the changeinformation recorded in the transaction ledger and records the copiedchange information in the virtual ledger (1070). That is, the groupaccount service providing server monitors whether the transactionoccurrence event or the information occurrence event is recorded in thetransaction ledger, and when it is determined that the transactionoccurrence event or the information occurrence event is recorded in thetransaction ledger, the group account service providing server copiesthe transaction occurrence event or the information occurrence event andrecords the transaction occurrence event or the information occurrenceevent in the virtual ledger.

Thereafter, the group account service providing server outputs thecontent recorded in the transaction ledger to the first agent (S1080)and outputs the content recorded in the virtual ledger to the secondagent (S1090).

As described above, according to the present invention, the groupaccount service providing server may generate the virtual ledger, inwhich the content of the transaction ledger is copied and recorded, toprovide the content of the transaction ledger to the host and providethe content of the virtual ledger to the participant, and thus the hostand the participant may share the content of the transaction ledger forthe group account in real time.

Hereinafter, a participant registration procedure will be described indetail with reference to FIG. 11. FIG. 11 is a flowchart illustrating amethod of performing a participant registration procedure according toan embodiment of the present invention.

As illustrated in FIG. 11, a first terminal generates a participantregistration request through a first agent and transmits the generatedparticipant registration request to a group account service providingserver (S1110). In an embodiment, the participant registration requestmay be generated by selecting at least one target person from among alist of persons registered in a first messenger agent installed in thefirst terminal by a host on the first agent. In this case, the groupaccount service providing server may classify and output a list ofpersons registered in the first messenger agent on the first agent intopreviously invited persons, uninvited persons, and persons waiting to beaccepted.

In another embodiment, the participant registration request may begenerated by selecting all persons registered in a chat room opened onthe first messenger agent by the host on the first agent.

When receiving the participant registration request from the firstterminal, the group account service providing server generates aparticipant subscription request message (S1120) and transmits thegenerated participant subscription request message to a second messengeragent installed in a second terminal of the target person (S1130). Inthis case, when there are a plurality of target persons, the groupaccount service providing server generates a participant subscriptionrequest message for all the target persons requested for registrationand transmits the participant subscription request message to a secondagent installed in the second terminal for each target person.

Thereafter, the second terminal generates an account subscriptionacceptance message and transmits the generated account subscriptionacceptance message to the group account service providing server(S1140). Specifically, when the participant subscription request messageis selected by the target person on the second messenger agent, thesecond terminal executes the second agent to generate the accountsubscription acceptance message using the second agent.

In the above-described embodiment, the group account service providingserver is described as transmitting the participant subscription requestmessage to the second messenger agent but, in another embodiment, thegroup account service providing server may directly transmit theparticipant subscription request message to the second agent. In thiscase, when the second agent is executed by the target person to selectthe participant subscription request message, the second terminal maygenerate the account subscription acceptance message.

When receiving the account subscription acceptance message from thesecond terminal, the group account service providing server registersthe target person as the participant of the group account (S1150) andrecords participant registration information for the target person inthe transaction ledger (S1160). In this case, the group account serviceproviding server may receive information about a messenger profile ofthe host and information about a messenger profile of the participant,which are obtained from the first messenger agent, from the first agentand record the information of the messenger profile of the host and theinformation of the messenger profile of the participant in thetransaction ledger.

When the participant registration information is recorded in thetransaction ledger, the group account service providing server copiesthe participant registration information recorded in the transactionledger and records the copied participant registration information inthe virtual ledger (S1170). The participant registration information isrecorded in the virtual ledger, and thus the participant registrationprocedure for the target person is completed.

Thereafter, the group account service providing server outputs thecontent recorded in the transaction ledger to the host(S1180) andoutputs the content recorded in the virtual ledger to the target personregistered as the participant (S1190). In this case, the group accountservice providing server may sequentially place and output the messengerprofiles recorded in the transaction ledger and the virtual ledger in apredetermined region on the first or second agent so that the messengerprofiles overlap some neighboring messenger profiles.

In FIGS. 10 and 11, the group account service providing server isdescribed as performing only the conversion into the group account andthe participant registration procedure, but the group account serviceproviding server according to the present invention may perform ageneral banking service such as deposit processing or withdrawalprocessing for the group account.

For example, when a membership fee payment request is generated by themember (the host or the participant), the group account serviceproviding server may perform membership fee payment processing. Inparticular, when the membership fee payment is performed, the groupaccount service providing server according to the present invention maywithdraw an amount according to a preset transfer condition from awithdrawal account of the member according to the preset transfercondition without setting a separate transfer condition andautomatically deposit the amount into the group account.

In an embodiment, the preset transfer condition may refer to a transfercondition in which the number for an account to be deposited themembership fee is set as the account number for the group account andthe deposit amount is set as the preset membership fee. In anotherembodiment, the preset transfer condition may refer to a transfercondition in which only the number for the account to be deposited themembership fee is automatically set as the account number for the groupaccount, and the deposit amount may be directly input from the member.

Meanwhile, the group account service providing server according to thepresent invention may process a Dutch treat request. Specifically, whenthe Dutch treat request is generated by the first agent, the groupaccount service providing server provides a Dutch treat payment iconthrough the first and second agents. When a Dutch treat payment requestis generated by selecting the Dutch treat payment icon by the member,the group account service providing server receives the Dutch treatpayment request and performs the Dutch treat payment processing. Whilethe Dutch treat payment processing is performed, the group accountservice providing server checks information about the withdrawal accountof the member in the Dutch treat payment request and withdraws theshared amount from the withdrawal account of the corresponding member todeposit the shared amount to the group account. In this case, the sharedamount to be withdrawn may be obtained from the Dutch treat paymentrequest registered in the transaction ledger.

The above description of the invention is only exemplary, and it will beunderstood by those skilled in the art that various modifications can bemade without departing from the scope of the present invention andwithout changing essential features.

For example, the configuration of the group account service providingserver illustrated in FIG. 2, the group account service providing methodillustrated in FIG. 10, or the participant registration procedureillustrated in FIG. 11 may be implemented in the form of a program suchas an application or an agent to be recorded on a medium capable ofreading the corresponding program. When the group account serviceproviding server, the group account service providing method, or theparticipant registration procedure according to the present invention isimplemented as a program, the components illustrated in FIG. 2 and theoperations illustrated in FIGS. 10 and 11 may be implemented as codes,and codes for implementing specific functions may be implemented as asingle program or may be implemented by being divided into a pluralityof programs.

When the present invention is implemented by being divided into aplurality of programs, the programs may be recorded on different media.For example, some of the functions may be installed in the group accountservice providing server, and the remaining functions may be implementedas the first agent or the second agent and installed in the firstterminal or the second terminal.

Therefore, the above-described embodiments should be considered in adescriptive sense only and not for purposes of limitation. Accordingly,the scope of the invention is not limited by the embodiments. The scopeof the invention is defined by the appended claims and encompasses allmodifications and equivalents that fall within the scope of the appendedclaims.

1.-25. (canceled)
 26. A group account service providing servercomprising: an account management unit configured to convert a firstaccount into a group account when a group account conversion request forthe first account of a host of a group is generated; a transactionledger management unit configured to record change information in atransaction ledger for the group account when the change informationincluding at least one of a transaction occurrence event and aninformation occurrence event is generated for the group account; avirtual ledger management unit configured to generate a virtual ledgerto be mapped to the transaction ledger when the first account is changedto the group account and copy the change information recorded in thetransaction ledger to record the copied change information in thevirtual ledger when the change information is recorded in thetransaction ledger, wherein the transaction ledger and the virtualledger each comprise one or more databases; and an interface unitconfigured to display the transaction ledger on a first agent installedin a first terminal of the host and display the virtual ledger on asecond agent installed in a second terminal of a participant sharing thegroup account, wherein the virtual ledger management unit is configuredto monitor change information of the transaction ledger in real time,and in response to determining that a change has occurred in thetransaction ledger after the first account is converted to the groupaccount, to copy new change information in the transaction ledger andrecord the copied new change information in the virtual ledger, whereinthe transaction occurrence event includes at least one of a depositevent and a withdrawal event, wherein the information occurrence eventincludes at least one of a memo related to the transaction occurrenceevent, one or more tags, a registration of the participant, a withdrawalof the participant, an announcement related to the group, a Dutch treatpayment request, setting information for the group account, andadditional information for the group account.
 27. The group accountservice providing server of claim 26, further comprising a participantmanagement unit configured to perform a participant registrationprocedure for a corresponding person when receiving a participantregistration request for at least one of persons registered in a firstmessenger agent installed in the first terminal from the first agent.28. The group account service providing server of claim 27, wherein,when the participant management unit receives a participant registrationrequest for all persons registered in a chat room opened on the firstmessenger agent from the first agent, the participant management unitperforms a participant registration procedure for all the personsrequested for registration.
 29. The group account service providingserver of claim 27, wherein the participant management unit transmits agroup account subscription request message to a second messenger agentinstalled in the second terminal of the person who is a subject of theparticipant registration request and registers the corresponding personas the participant when an account subscription acceptance message isreceived from the second agent executed by selecting the group accountsubscription request message output on the second messenger agent. 30.The group account service providing server of claim 26, furthercomprising a deposit and withdrawal management unit configured toautomatically set an account number of a deposit account to an accountnumber of the group account and automatically set an amount to bedeposited to the membership fee to set transfer conditions when amembership fee payment icon on the first and second agents is selectedand configured to withdraw the membership fee from a withdrawal accountset in the first and second agents and transfer the deposit amount tothe group account when the setting of the transfer conditions iscompleted.
 31. The group account service providing server of claim 26,further comprising a deposit and withdrawal management unit configuredto determine the host or the participant for which a deposit event doesnot occur on a preset membership fee payment date when the presetmembership fee payment date arrives and configured to generate amembership fee payment message for the determined host or participant,wherein the interface unit provides the membership fee payment messageto the first agent or a first messenger agent installed in the firstterminal for the host or to the second agent or a second messenger agentinstalled in the second terminal for the participant.
 32. The groupaccount service providing server of claim 26, wherein: when a Dutchtreat payment request including an amount spent, the number of membersto share the amount spent, and an amount shared by each member isgenerated through the first agent, the transaction ledger managementunit records the Dutch treat payment request in the transaction ledger;the virtual ledger management unit copies the Dutch treat paymentrequest recorded in the transaction ledger and records the copied Dutchtreat payment request in the virtual ledger; and the interface unitprovides a Dutch treat payment icon corresponding to the Dutch treatpayment request to the first and second agents.
 33. The group accountservice providing server of claim 26, wherein, when a request formasking processing for at least a portion of an abstract of thetransaction occurrence event is generated from the first agent, theinterface unit masks a portion for which the masking processing isrequested from among the abstract of the transaction occurrence eventrecorded in the virtual ledger and provides the masked portion to thesecond agent.
 34. The group account service providing server of claim26, wherein: the transaction ledger management unit records informationabout messenger profiles of the host and the participants obtained froma first messenger agent installed in the first terminal in thetransaction ledger; the virtual ledger management unit copies theinformation about the messenger profiles of the host and theparticipants recorded in the transaction ledger and records theinformation about the messenger profiles in the virtual ledger; and theinterface unit sequentially places and outputs the messenger profiles ina predetermined region on the first and second agents, wherein themessenger profiles are placed so that some of adjacent messengerprofiles overlap.
 35. The group account service providing server ofclaim 26, wherein: when the group account conversion request isgenerated, the account management unit assigns a safe account numberdifferent from a real account number for the first account to the groupaccount; and the interface unit allows the real account number for thefirst account to be displayed through the first agent and allows thesafe account number to be displayed through the second agent.
 36. Thegroup account service providing server of claim 26, further comprising asearch unit configured to classify a membership fee payment historyrecorded in the transaction ledger according to a membership fee paymentdate, a name of the host, and a name of the participant and provide aresult of the search, wherein the interface unit provides the classifiedmembership fee payment history through the first agent.
 37. A groupaccount service providing method comprising: converting a first accountinto a group account in response to a group account conversion requestfor the first account of a host of a group; generating a virtual ledgerto be mapped to a transaction ledger of the group account, wherein thetransaction ledger and the virtual ledger each comprise one or moredatabases; recording change information in the transaction ledger whenthe change information including at least one of a transactionoccurrence event and an information occurrence event is generated forthe group account; when the change information is recorded in thetransaction ledger, monitoring the transaction ledger and copying andrecording the change information in the virtual ledger; and outputtingcontents recorded in the transaction ledger to a first agent installedin a first terminal of the host and outputting contents recorded in thevirtual ledger to a second agent installed in a second terminal of theparticipant sharing the group account, wherein the virtual ledgermanagement unit monitors change information of the transaction leger inreal time, and in response to determining that a change has occurred inthe transaction ledger after the first account is converted to the groupaccount, copies new change information and records the copied new changeinformation in the virtual ledger, wherein the transaction occurrenceevent includes at least one of a deposit event and a withdrawal event,wherein the information occurrence event includes at least one of a memorelated to the transaction occurrence event, one or more tags, aregistration of the participant, a withdrawal of the participant, anannouncement related to the group, a Dutch treat payment request,setting information for the group account, and additional informationfor the group account.
 38. The group account service providing method ofclaim 37, further comprising, when a participant registration requestfor at least one of the persons registered in a first messenger agentinstalled in the first terminal is received from the first agent,performing a participant registration procedure for a person requestedfor registration.
 39. The group account service providing method ofclaim 38, wherein, in the performing of the participant registrationprocedure, a list of the persons registered in the first messenger agentis output through the first agent, and persons are classified intopre-registered persons, persons waiting to be accepted, and unregisteredpersons to be output in the list of the persons.
 40. The group accountservice providing method of claim 37, further comprising, when aparticipant registration request for all persons registered in a chatroom opened on a first messenger agent installed in the first terminalis received from the first agent, performing a participant registrationprocedure for all the persons requested for registration.
 41. The groupaccount service providing method of claim 37, further comprising: when amembership fee payment icon is selected through the first or secondagent, automatically setting an account number of a deposit account toan account number of the group account and automatically setting anamount to be deposited to a preset membership fee to set transferconditions; and withdrawing the membership fee from a withdrawal accountset in the first or second agent according to the set transferconditions and transferring the amount to be deposited to the groupaccount.
 42. The group account service providing method of claim 37,further comprising: receiving a Dutch treat payment request including anamount spent, the number of members to share the amount spent, and anamount shared by each member from the first agent; providing a Dutchtreat payment icon corresponding to the Dutch treat payment request tothe first or second agent; when the Dutch treat payment icon is selectedby the host or the participant, automatically setting an account numberof a deposit account to an account number of the group account andautomatically setting an amount to be deposited to the shared amount toset transfer conditions; and withdrawing the shared amount from thewithdrawal account set in the first or second agent according to the settransfer conditions and transferring the deposit amount to the groupaccount.
 43. The group account service providing method of claim 37,further comprising: obtaining information about messenger profiles ofthe host and the participants from a first messenger agent installed inthe first terminal; and sequentially placing and outputting themessenger profiles in a predetermined region on the first or secondagent, wherein the messenger profiles are placed so that some ofadjacent messenger profiles overlap to output.
 44. The group accountservice providing method of claim 37, further comprising assigning asafe account number different from a real account number of the firstaccount to the group account, wherein the real account number of thefirst account is output on the first agent and the safe account numberis output on the second agent.